Time domain resource allocation for pusch transmission

ABSTRACT

The embodiments herein relate to time domain resource allocation for PUSCH transmission. In one embodiment, there proposes a method in a wireless communication device for Random Access (RA), comprising: transmitting a preamble on Physical Random Access Channel (PRACH); receiving a Random Access Response (RAR) message; transmitting, on Physical Uplink Shared Channel (PUSCH), a message for terminal identification (Msg3), wherein the time resource allocation of Msg3 is different than the time resource allocation of other message to be transmitted on the PUSCH (normal PUSCH). The embodiments herein can support flexible time resource allocation configuration for Msg3, and at the same time, the signaling overhead in RAR/DCI for indicating the time resource allocation of PUSCH carrying Msg3 can be reduced.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/290,772, filed Mar. 1, 2019, which claims priority to and the benefitof International Application No. PCT/CN2018/077942, filed Mar. 2, 2018and entitled “TIME DOMAIN RESOURCE ALLOCATION FOR PUSCH TRANSMISSION.”

TECHNICAL FIELD

The embodiments herein relate generally to the field of wirelesscommunication, and more particularly, the embodiments herein relate totime domain resource allocation for PUSCH transmission.

BACKGROUND Random Access Procedure

A random access (RA) procedure is a key function in a cellular system.In Long term Evolution (LTE), a UE that would like to access the networkinitiates the random access procedure by transmitting a preamble (Msg1)in the uplink on the Physical Random Access Channel (PRACH). A gNB (nextgeneration Node B, or TRP, Transmission and Reception Point, i.e. a basestation, access node) receiving the preamble and detecting therandom-access attempt will respond in the downlink by transmitting arandom access response (RAR, Msg2). The RAR carries an uplink schedulinggrant for the UE to continue the procedure by transmitting a followingsubsequent message in the uplink (Msg3) for terminal identification. Asimilar procedure is envisioned for NR (New Radio, for example, 5G, orbeyond); see an illustration in FIG. 1. FIG. 1 is a schematic signalingchart showing the messages in the random access procedure.

Before transmission of the PRACH preamble, the UE receives both a set ofsynchronization signals and configuration parameters on a broadcastchannel in an SS-block (e.g., NR-PSS, NR-SSS, NR-PBCH), possiblycomplemented with configuration parameters received on yet anotherchannel.

Msg3 Transmission

Msg3 is transmitted by using a PUSCH channel. Besides Msg3 payload,Demodulation Reference Signal (DMRS) is also transmitted to assist thedata decoding at the eNB/gNB. In both LTE and NR, for 4-step randomaccess procedure, the initial transmission of Msg3 is scheduled by theUL grant contained in RAR. The retransmission of Msg3 is scheduled by ULgrant over PDCCH. In LTE, Msg3 repetition can be configured by the ULgrant contained in RAR for coverage enhancements for BL/CE UEs.

UL Grant in RAR in LTE and NR

In LTE, The Uplink Grant field in RAR, also referred to as random accessresponse grant field, indicates the resources to be used on the uplink.The size of the UL Grant field is 20 bits for Non-BL/CE UEs. The contentof these 20 bits starting with the MSB and ending with the LSB are asfollows:

Hopping flag—1 bit

Fixed size resource block assignment—10 bits

Truncated modulation and coding scheme—4 bits

If a UE is configured with a higher layer parameterpusch-EnhancementsConfig, then

Repetition number of Msg3—3 bits else

TPC command for scheduled PUSCH—3 bits

UL delay—1 bit

CSI request—1 bit.

For NB-IoT UEs, the size of UL grant field is 15 bits, and for BL UEsand UEs in enhanced coverage level 2 or 3, the size of the UL grantfield is 12 bits. The contents of the UL grant are listed in Table 6-2TS 36.213 for BL/CE UE. The detailed design of UL grant in RAR for NR isunder discussion.

Resource Allocation for Msg3 in LTE

The frequency resource assignment is indicated by the fixed sizeresource block assignment field in the UL grant contained in RAR. TheMsg3 transmission timing for a non-BL/CE UE (without repetition) isdefined as follows:

If a PDCCH with associated RA-RNTI is detected in subframe n, and thecorresponding DL-SCH transport block contains a response to thetransmitted preamble sequence, the UE shall, according to theinformation in the response, transmit an UL-SCH transport block in thefirst subframe n+k₁, k₁≥6, if the UL delay field in RAR is set to zerowhere n+k₁ is the first available UL subframe for PUSCH transmission,where for TDD serving cell, the first UL subframe for PUSCH transmissionis determined based on the UL/DL configuration (i.e., the parametersubframeAssignment) indicated by higher layers. The UE shall postponethe PUSCH transmission to the next available UL subframe after n+k₁ ifthe field is set to 1.

For BL/CE UE configured with a number of Msg3 PUSCH repetitions, A, theUE shall postpone the PUSCH transmission to the next available ULsubframe after n++A if the UL delay field is set to 1.

Time Domain Allocation of PDSCH/PUSCH in NR

Currently time domain allocation of PDSCH (PUSCH) in NR has not beenfinalized in RANI yet, some agreements were met in RANI #90bis meeting.

For RRC connected mode, a time resource allocation table with 16 rows issignaled by RRC signaling to a UE per bandwidth part. Then, an index inthe scheduling DCI will indicate the exact time resource allocation forPDSCH.

Agreements from RANI #90bis:

-   -   For both slot and mini-slot, the scheduling DCI can provide an        index into a UE-specific table giving the OFDM symbols used for        the PDSCH (or PUSCH) transmission:

i. starting OFDM symbol and length in OFDM symbols of the allocation

ii. FFS: one or more tables

iii. FFS: including the slots used in case of multi-slot/multi-mini-slotscheduling or slot index for cross-slot scheduling

iv. FFS: May need to revisit if SFI support non-contiguous allocations

-   -   At least for Remaining Minimum System Information (RMSI)        scheduling

i. At least one table entry needs to be fixed in the spec.

Subcarrier Spacing (SCS) of Msg3 in NR

NR supports RACH configuration in (RMSI) containing 1 bit to convey SCSof Msg3. In sub-6 GHz, subcarrier spacing of Msg3 can be either 15 or 30kHz. In over-6 GHz, subcarrier spacing of Msg3 can be either 60 or 120kHz.

SUMMARY Timing for Msg3 Transmission and Normal PUSCH in NR

In section 8.3 of TS 38.213 a minimum time between the last symbol onPDSCH contains RAR and the first symbol UE of a corresponding Msg3 PUSCHtransmission is defined as N_t1+N_t2+N_ta_max+0.5 ms. N_t1 and N_t2 isthe UE processing time that defined in a table in TS 38.214. Fornumerology 1, N_t1+N_t2 gives about 22 to 25 symbols, N_ta_max is themaximum timing adjustment value that can be provided by TA command inRAR, which is approximately 2 slots. For normal PUSCH transmission, itrequires only N_t2 that is 12 symbols.

The timing for Msg3 differs from normal PUSCH transmissions. For initialMSG3 transmission gNB should take into account the necessary UEprocessing time that is 0.5 ms to handle the MAC packet for allnumerologies, the N1 and N2, and the timing advance with range of 0 to 2slots. It will be difficult to cover K2 in a single table for bothnormal PUSCH and Msg3 supporting all numerologies with 16 rows.

For NR random access, a new signaling is needed for indicating the timeresource assignment for Msg3 transmission/retransmission/repetition,including the starting position and/or the transmission duration, and/orthe DMRS configuration associated to the Msg3 transmission/repetition.

In the embodiments, a default time resource allocation table ispredefined for normal PUSCH to indicate the timing K2, the startingsymbol, and PUSCH length. The timing for PUSCH carrying Msg3 isindicated by using a different between K2 for normal PUSCH and PUSCHcarrying Msg3.

In one embodiment, there proposes a method in a wireless communicationdevice for Random Access (RA), comprising: transmitting a preamble onPhysical Random Access Channel (PRACH); receiving a Random AccessResponse (RAR) message; transmitting, on Physical Uplink Shared Channel(PUSCH), a message for terminal identification, wherein the timeresource allocation of the message for terminal identification isdifferent than the time resource allocation of other message to betransmitted on the PUSCH.

In another embodiment, there proposes a method in a network node forRandom Access (RA), comprising: receiving a preamble on Physical RandomAccess Channel (PRACH); transmitting a Random Access Response (RAR)message; receiving, on Physical Uplink Shared Channel (PUSCH), a messagefor terminal identification, wherein the time resource allocation of themessage for terminal identification is different than the time resourceallocation of other message to be transmitted on the PUSCH.

In yet another embodiment, there proposes a wireless communicationdevice, comprising: at least one processor; and a non-transitorycomputer readable medium coupled to the at least one processor, thenon-transitory computer readable medium contains instructions executableby the at least one processor, whereby the at least one processor isconfigured to: transmit a preamble on Physical Random Access Channel(PRACH); receive a Random Access Response (RAR) message; transmit, onPhysical Uplink Shared Channel (PUSCH), a message for terminalidentification, wherein the time resource allocation of the message forterminal identification is different than the time resource allocationof other message to be transmitted on the PUSCH.

In yet another embodiment, there proposes a network node, comprising: atleast one processor; and a non-transitory computer readable mediumcoupled to the at least one processor, the non-transitory computerreadable medium contains instructions executable by the at least oneprocessor, whereby the at least one processor is configured to: receivea preamble on Physical Random Access Channel (PRACH); transmit a RandomAccess Response (RAR) message; receive, on Physical Uplink SharedChannel (PUSCH), a message for terminal identification, wherein the timeresource allocation of the message for terminal identification isdifferent than the time resource allocation of other message to betransmitted on the PUSCH.

In yet another embodiment, there proposes a computer readable mediumcomprising computer readable code, which when run on an apparatus,causes the apparatus to perform any of the above method.

The method herein can support flexible time resource allocationconfiguration for Msg3, and at the same time, the signaling overhead inRAR/DCI for indicating the time resource allocation of PUSCH carryingMsg3 can be reduced.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form partof the specification, illustrate various embodiments of the presentdisclosure and, together with the description, further serve to explainthe principles of the disclosure and to enable a person skilled in thepertinent art to make and use the embodiments disclosed herein. In thedrawings, like reference numbers indicate identical or functionallysimilar elements, and in which:

FIG. 1 is a schematic signaling chart showing the messages in the randomaccess procedure;

FIG. 2 is a schematic block diagram showing an example wirelesscommunication system, in which the embodiments herein can beimplemented;

FIG. 3 is a schematic flow chart showing an example method in a wirelesscommunication device, according to the embodiments herein;

FIG. 4 is a schematic flow chart showing an example method in a networknode, according to the embodiments herein;

FIG. 5 is a schematic block diagram showing an example wirelesscommunication device, according to the embodiments herein;

FIG. 6 is a schematic block diagram showing an example network node,according to the embodiments herein;

FIG. 7 is a schematic block diagram showing an apparatus, according tothe embodiments herein.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments herein will be described in detail hereinafter withreference to the accompanying drawings, in which embodiments are shown.These embodiments herein may, however, be embodied in many differentforms and should not be construed as being limited to the embodimentsset forth herein. The elements of the drawings are not necessarily toscale relative to each other.

Reference to “one embodiment” or “an embodiment” means that a particularfeature, structure or characteristic described in connection with theembodiment is included in at least one embodiment. Thus, the appearancesof the phrase “in one embodiment” appearing in various places throughoutthe specification are not necessarily all referring to the sameembodiment.

The term “A, B, or C” used herein means “A” or “B” or “C”; the term “A,B, and C” used herein means “A” and “B” and “C”; the term “A, B, and/orC” used herein means “A”, “B”, “C”, “A and B”, “A and C”, “B and C” or“A, B, and C”. Furthermore, the singular wording “a”, “an”, and/or “the”element also intends to cover a plurality of such elements, and thus maymeans “one or more”.

In the embodiments herein, a default time resource allocation table ispredefined for normal PUSCH to indicate the timing K2, the startingsymbol, and PUSCH length. The timing for PUSCH carrying Msg3 isindicated by using a different between K2 for normal PUSCH and PUSCHcarrying Msg3.

FIG. 2 shows a schematic diagram of an example wireless communicationsystem 200, in which the embodiments can be implemented. In oneembodiment, the wireless communication system 200 may include at leastone wireless communication device 201 and at least one network node 202.However, the embodiments herein do not limit the number of the wirelesscommunication device 201 and the network node 202.

In one embodiment, the wireless communication system 200 may be embodiedas for example UE, device to device (D2D) UE, proximity capable UE(i.e., ProSe UE), machine type UE or UE capable of machine to machine(M2M) communication, Personal Digital Assistant (PDA), PAD, Tablet,mobile terminals, smart phone, laptop embedded equipped (LEE), laptopmounted equipment (LME), USB dongles, etc.

In one embodiment, the network node 202 may be embodied as for exampleeNodeB (eNB), Base Station (BS), network controller, radio networkcontroller (RNC), base station controller (BSC), relay, donor nodecontrolling relay, base transceiver station (BTS), access point (AP),transmission points, transmission nodes, etc. In one embodiment, thenetwork node 202 may be a gNB (next generation Node B). In oneembodiment, the wireless communication system 200 may be configured inan Over The Top (OTT) scenario.

The time resource assignment configuration for Msg3 transmission in NRshould consider the minimum gap between RAR and Msg3 specified in NR andthe semi-static TDD configuration indicated by higher layer parameters,e.g., in RMSI or Radio Resource Control (RRC). The time resourceconfiguration for Msg3 transmission/retransmission/repetition shouldalso be a function of at least the transmission duration, and/or, DMRSconfiguration, and/or starting position.

In one embodiment, at least one default time resource allocation table(Table A) is predefined for PUSCH other than Msg3 (referred to as normalPUSCH). A default table (Table B) is predefined for Msg3 to indicate thedifference of K2 values between PUSCH carrying Msg3 and normal PUSCH(referred to as K2 offset).

In one embodiment, the K2 offset table (Table B) is formed by aone-to-one mapping between the K2 offset value and the numerology. Forexample, the table B1 below:

TABLE B1 Numerology (subcarrier spacing) 0 1 2 3 (15 KHz) (30 KHz) (60KHz) (120 KHz) K2 offset (in slot) 2 2 4 5

In another embodiment, the K2 offset table (Table B) supports multipleK2 offset values per numerology or for some numerologies. The K2 offsetvalue used for PUSCH carrying Msg3 is indicated by some reserved orunused bits in RAR. For example, the time resource allocation field inUL grant in RAR has 4 bits, where 3 bits are used for indicating the rowindex of Table A, 1 bit is used to signal the K2 offset to choose fromTable B. For example, the table B2 below:

TABLE B2 Numerology (subcarrier spacing) 0 1 2 3 (15 KHz) (30 KHz) (60KHz) (120 KHz) K2 offset (in slot) {1, 2} 2 {3, 4} 5

The time resource allocation for PUSCH carrying Msg3 is indicated byusing the default K2 offset table (Table B) together with the defaulttime resource allocation table for normal PUSCH (Table A).

The starting position and symbol length for PUSCH carrying Msg3 isindicated by the time domain resource allocation field in the UL grantin RAR. The time domain resource allocation field in RAR indicates therow index of Table A, that is used for the UE to read the information ofK2 for normal PUSCH, starting symbol position and length of PUSCHcarrying Msg3. The K2 value for PUSCH carrying Msg3 is obtained by theK2 for normal PUSCH+K2 offset.

In one embodiment, a single default time allocation table (Table C) isused for both normal PUSCH and PUSCH carrying Msg3. This Table C can beformed by combing Table A and Table B per numerology.

By the embodiments herein, a default time resource allocation table ispredefined for normal PUSCH to indicate the timing K2, the startingsymbol, and PUSCH length. The timing for PUSCH carrying Msg3 isindicated by using a different between K2 for normal PUSCH and PUSCHcarrying Msg3.

FIG. 3 is a schematic flow chart showing an example method 300 in awireless communication device, according to the embodiments herein. Inone embodiment, the flow chart in FIG. 3 can be implemented in thewireless communication device 201 in FIG. 2.

The method 300 may begin with step S301, in which the wirelesscommunication device 201 may transmit a preamble on Physical RandomAccess Channel (PRACH) (Msg1). Then, the method 300 may proceed to stepS302, in which the wireless communication device 201 may receiving a RARmessage (Msg2) sent by the network node 202 in response to the preamble.Then, the method 300 may proceed to step S303, in which the wirelesscommunication device 201 may transmit, on Physical Uplink Shared Channel(PUSCH), a message for terminal identification (Msg3). Then, althoughnot shown, the wireless communication device 201 may further receive aContention Resolution Message (CRM) (Msg4) from the network node 202. Inone embodiment herein, the time resource allocation(s) of Msg3 isdifferent than the time resource allocation of any other message(s) tobe transmitted on the PUSCH (may be referred as normal PUSCH herein).

In one embodiment, the time resource allocation(s) of the Msg3 has atiming offset (which may be referred as K2 offset) from the timeresource allocation of the other message to be transmitted on the PUSCH.In one embodiment, the time resource allocation(s) of the Msg3 may beused to specify a minimum time between the last symbol on PDSCH containsRAR and the first symbol UE of a corresponding Msg3 PUSCH transmission.Note that, there may be only one time resource allocation or a pluralityof time resource allocations.

In one embodiment, the time resource allocation of the normal PUSCH maydepend on the numerology used. For example, the time resource allocationof the normal PUSCH may depend on the subcarrier spacing (SCS) used, orthe other parameter.

In one embodiment, the time resource allocation of the normal PUSCH isindicated by the network node 202 via Remaining Minimum SystemInformation (RMSI), RRC, and/or Downlink Control Information (DCI). Inone embodiment, the time resource allocation of the normal PUSCH isindicated by the network node 202 via any other message(s).

In one embodiment, the time resource allocation of the normal PUSCH maybe placed and/or transmitted in a first predefined table or a firstconfigured table (may be referred as table A). In one embodiment, morethan one table A is defined.

In one embodiment, the timing offset (i.e., K2 offset) may also dependon the numerology used. In one approach, there may be a one-to-onemapping between the K2 offset value and the numerology. In anotherapproach, for one numerology, there may be more than one possible K2offset. As used herein, the numerology may include the subcarrierspacing (SCS) used, or the other parameter.

In one embodiment, the timing offset (K2 offset) may be also indicatedby a network node via RMSI, RRC, DCI, and/or any other messages. In oneembodiment, the timing offset (K2 offset) may be also indicated by thenetwork node 202 in the RAR message (Msg2). In one embodiment, there isno necessary for the network node 202 to indicate the timing offset (K2offset), since the wireless communication device 201 (for example UE)has known the K2 offset to be used for Msg3 in advance.

In one embodiment, the K2 offset may be placed and/or transmitted in asecond predefined table or a second configured table (may be referred astable B). For example, for one-to-one mapping between the K2 offsetvalue and the numerology, the table B may be embodied as the abovementioned table B 1. Furthermore, as another example, the table B may beembodied as the above mentioned table B2, in which there may be morethan one alternative K2 offset value for one numerology.

In one embodiment, the table A and the table B may be merged into asingle default time allocation table (Table C), which is used for bothnormal PUSCH and PUSCH carrying Msg3. This Table C can be formed bycombing Table A and Table B per numerology.

The above steps are only examples, and the wireless communication device201 can perform any actions described in connection to FIG. 2.

FIG. 4 is a schematic flow chart showing an example method 400 in thenetwork node, according to the embodiments herein. In one embodiment,the flow chart in FIG. 4 can be implemented in the network node 202 inFIG. 2.

The method 400 may begin with step S401, in which the network node 202may receive a preamble on Physical Random Access Channel (PRACH) (Msg1),and the preamble may indicate a wireless communication device (UE)attempting to access to the network node 202. Of course, there may bemore than one UE attempting to access to the network node 202. Then, themethod 400 may proceed to step S402, in which the network node 202 maytransmit a RAR message (Msg2) to the UE(s) attempting to access to thenetwork node 202, in response to the preamble. The Msg2 may includeUplink (UL) grant for one or more UE. Then, the method 400 may proceedto step S403, in which the network node 202 may receive, on PhysicalUplink Shared Channel (PUSCH), a message for terminal identification(Msg3), from the one or more UE. Then, although not shown, the networknode 202 may further transmit a Contention Resolution Message (CRM)(Msg4) to the one or more UE. In one embodiment herein, the timeresource allocation(s) of Msg3 is different than the time resourceallocation of any other message(s) to be transmitted on the PUSCH (maybe referred as normal PUSCH herein).

In one embodiment, the time resource allocation(s) of the Msg3 has atiming offset (which may be referred as K2 offset) from the timeresource allocation of the other message to be transmitted on the PUSCH.In one embodiment, the time resource allocation(s) of the Msg3 may beused to specify a minimum time between the last symbol on PDSCH containsRAR and the first symbol UE of a corresponding Msg3 PUSCH transmission.Note that, there may be only one time resource allocation or a pluralityof time resource allocations.

In one embodiment, the time resource allocation of the normal PUSCH maydepend on the numerology used. For example, the time resource allocationof the normal PUSCH may depend on the subcarrier spacing (SCS) used, orthe other parameter.

In one embodiment, the network node 202 may indicate the time resourceallocation of the normal PUSCH via RMSI, RRC, and/or DCI. In oneembodiment, the network node 202 may indicate the time resourceallocation of the normal PUSCH via any other message(s).

In one embodiment, the time resource allocation of the normal PUSCH maybe placed and/or transmitted in a first predefined table or a firstconfigured table (may be referred as table A). In one embodiment, morethan one table A is defined.

In one embodiment, the timing offset (i.e., K2 offset) may also dependon the numerology used. In one approach, there may be a one-to-onemapping between the K2 offset value and the numerology. In anotherapproach, for one numerology, there may be more than one possible K2offset. As used herein, the numerology may include the subcarrierspacing (SCS) used, or the other parameter.

In one embodiment, the network node 202 may also indicate the timingoffset (K2 offset) via RMSI, RRC, DCI, and/or any other messages. In oneembodiment, the network node 202 may indicate the timing offset (K2offset) in the RAR message (Msg2). In one embodiment, there is nonecessary for the network node 202 to indicate the timing offset (K2offset), since the wireless communication device 201 (for example UE)has known the K2 offset to be used for Msg3 in advance.

In one embodiment, the K2 offset may be placed and/or transmitted in asecond predefined table or a second configured table (may be referred astable B). For example, for one-to-one mapping between the K2 offsetvalue and the numerology, the table B may be embodied as the abovementioned table B 1. Furthermore, as another example, the table B may beembodied as the above mentioned table B2, in which there may be morethan one alternative K2 offset value for one numerology.

In one embodiment, the table A and the table B may be merged into asingle default time allocation table (Table C), which is used for bothnormal PUSCH and PUSCH carrying Msg3. This Table C can be formed bycombing Table A and Table B per numerology.

The above steps are only examples, and the network node 202 can performany actions described in connection to FIG. 2.

FIG. 5 is a schematic block diagram showing an example wirelesscommunication device 201, according to the embodiments herein.

In one embodiment, the wireless communication device 201 may include atleast one processor 501; and a non-transitory computer readable medium502 coupled to the at least one processor 501. The non-transitorycomputer readable medium 502 contains instructions executable by the atleast one processor 501, whereby the at least one processor 501 isconfigured to perform the steps in the example method 300 as shown inthe schematic flow chart of FIG. 3; the details thereof is omitted here.

Note that, the wireless communication device 201 can be embodied inhardware, software, firmware, and/or any combination thereof. Forexample, the wireless communication device 201 may include a pluralityof units, circuities, or modules, each of which can be used to perform astep of the example method 300 or any step shown in FIG. 2 related tothe wireless communication device 201.

FIG. 6 is a schematic block diagram showing an example network node 202,according to the embodiments herein.

In one embodiment, the network node 202 may include at least oneprocessor 601; and a non-transitory computer readable medium 602 coupledto the at least one processor 601. The non-transitory computer readablemedium 602 contains instructions executable by the at least oneprocessor 601, whereby the at least one processor 601 is configured toperform the steps in the example method 400 as shown in the schematicflow chart of FIG. 4; the details thereof is omitted here.

Note that, the network node 202 can be embodied in hardware, software,firmware, and/or any combination thereof. For example, the network node202 may include a plurality of units, circuities, or modules, each ofwhich can be used to perform a step of the example method 400 or anystep shown in FIG. 2 related to the network node 202.

FIG. 7 is a schematic block diagram showing an apparatus 700, accordingto the embodiments herein. In one embodiment, the apparatus 700 can beconfigured as any of the above mentioned apparatuses, such as thewireless communication device 201 or the network node 202.

In one embodiment, the apparatus 700 may include but not limited to atleast one processor such as Central Processing Unit (CPU) 701, acomputer-readable medium 702, and a memory 703. The memory 703 maycomprise a volatile (e.g. Random Access Memory, RAM) and/or non-volatilememory (e.g. a hard disk or flash memory). In one embodiment, thecomputer-readable medium 702 may be configured to store a computerprogram and/or instructions, which, when executed by the processor 701,causes the processor 701 to carry out any of the above mentionedmethods.

In one embodiment, the computer-readable medium 702 (such asnon-transitory computer readable medium) may be stored in the memory703. In another embodiment, the computer program can be stored in aremote location for example computer program product 704 (also can beembodied as computer-readable medium), and accessible by the processor701 via for example carrier 705.

The computer-readable medium 702 and/or the computer program product 704can be distributed and/or stored on a removable computer-readablemedium, e.g. diskette, CD (Compact Disk), DVD (Digital Video Disk),flash or similar removable memory media (e.g. compact flash, SD (securedigital), memory stick, mini SD card, MMC multimedia card, smart media),HD-DVD (High Definition DVD), or Blu-ray DVD, USB (Universal Serial Bus)based removable memory media, magnetic tape media, optical storagemedia, magneto-optical media, bubble memory, or distributed as apropagated signal via a network (e.g. Ethernet, ATM, ISDN, PSTN, X.25,Internet, Local Area Network (LAN), or similar networks capable oftransporting data packets to the infrastructure node).

Example embodiments are described herein with reference to blockdiagrams and/or flowchart illustrations of computer-implemented methods,apparatus (systems and/or devices) and/or non-transitory computerprogram products. It is understood that a block of the block diagramsand/or flowchart illustrations, and combinations of blocks in the blockdiagrams and/or flowchart illustrations, can be implemented by computerprogram instructions that are performed by one or more computercircuits. These computer program instructions may be provided to aprocessor circuit of a general purpose computer circuit, special purposecomputer circuit, and/or other programmable data processing circuit toproduce a machine, such that the instructions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, transform and control transistors, values stored in memorylocations, and other hardware components within such circuitry toimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks, and thereby create means (functionality)and/or structure for implementing the functions/acts specified in theblock diagrams and/or flowchart block(s).

These computer program instructions may also be stored in a tangiblecomputer-readable medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks. Accordingly, embodiments of present inventiveconcepts may be embodied in hardware and/or in software (includingfirmware, resident software, micro-code, etc.) that runs on a processorsuch as a digital signal processor, which may collectively be referredto as “circuitry,” “a module” or variants thereof.

Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present inventiveconcepts. All such variations and modifications are intended to beincluded herein within the scope of present inventive concepts.Accordingly, the above disclosed subject matter is to be consideredillustrative, and not restrictive, and the appended examples ofembodiments are intended to cover all such modifications, enhancements,and other embodiments, which fall within the spirit and scope of presentinventive concepts. Thus, to the maximum extent allowed by law, thescope of present inventive concepts are to be determined by the broadestpermissible interpretation of the present disclosure including thefollowing examples of embodiments and their equivalents, and shall notbe restricted or limited by the foregoing detailed description.

ABBREVIATIONS

3GPP Third Generation Partnership Project

CRM Contention Resolution Message

DCI Downlink Control Information

DMRS Demodulation Reference Signal

LTE Long-Term Evolution

NR New Radio

OFDM Orthogonal Frequency Division Multiplexing

OTT Over The Top

PBCH Physical Broadcast Channel

PDCCH Physical Downlink Control Channel

PDSCH Physical Downlink Shared Channel

PRACH Physical Random Access Channel

PSS Primary Synchronization signal

PUSCH Physical Uplink Shared Channel

RA Random Access

RAN Radio Access Network

RAR Random Access Response

RMSI Remaining Minimum System Information

RRC Radio Resource Control

SCS Subcarrier Spacing

SSS Secondary Synchronization signal

TDD Time Division Duplexing

UL Uplink.

1-20. (canceled)
 21. A method of operating a wireless communicationdevice, the method comprising: transmitting a preamble on a PhysicalRandom Access Channel (PRACH); receiving a Random Access Response (RAR)message containing an uplink (UL) grant; transmitting, on a PhysicalUplink Shared Channel (PUSCH), a first message wherein the first messageis scheduled by the RAR message and has a first time resourceallocation; and transmitting, on the PUSCH, a second message wherein thesecond message is not scheduled by the RAR message and has a second timeresource allocation, the first and second time resource allocationsbeing different by a predetermined timing offset.
 22. The method ofclaim 21, wherein the first message is an Msg3 message and the secondmessage is a non-Msg3 message.
 23. The method of claim 21, wherein thepredetermined timing offset is based on a numerology.
 24. The method ofclaim 21, wherein the predetermined timing offset corresponds to anumerology according to: numerology 0 2 offset in unit of slot 2
 4.


25. The method of claim 21, wherein the predetermined timing offsetapplies to the first time resource allocation.
 26. The method of claim21, wherein the predetermined timing offset applies to the second timeresource allocation.
 27. The method of claim 21, wherein thepredetermined timing offset depends on a numerology used, and there isone timing offset for one numerology.
 28. The method of claim 21,wherein the predetermined timing offset depends on a numerology used,and there is more than one timing offset for one numerology.
 29. Themethod of claim 21, wherein the predetermined timing offset is indicatedin the RAR message.
 30. A wireless communication device comprising: aprocessor; and a non-transitory computer readable medium incommunication with the processor, the non-transitory computer readablemedium storing instructions executable by the processor, whereby theprocessor is configured to perform operations comprising: transmitting apreamble on a Physical Random Access Channel (PRACH); receiving a RandomAccess Response (RAR) message containing an uplink (UL) grant;transmitting, on a Physical Uplink Shared Channel (PUSCH), a firstmessage wherein the first message is scheduled by the RAR message andhas a first time resource allocation; and transmitting, on the PUSCH, asecond message wherein the second message is not scheduled by the RARmessage and has a second time resource allocation, the first and secondtime resource allocations being different by a predetermined timingoffset.
 31. The wireless communication device of claim 30, wherein thefirst message is an Msg3 message and the second message is a non-Msg3message.
 32. The wireless communication device of claim 30, wherein thepredetermined timing offset is based on a numerology.
 33. The wirelesscommunication device of claim 30, wherein the predetermined timingoffset corresponds to a numerology according to: numerology 0 2 offsetin unit of slot 2
 4.


34. The wireless communication device of claim 30, wherein thepredetermined timing offset applies to the first time resourceallocation.
 35. The wireless communication device of claim 30, whereinthe predetermined timing offset applies to the second time resourceallocation.
 36. The wireless communication device of claim 30, whereinthe predetermined timing offset depends on a numerology used, and thereis one timing offset for one numerology.
 37. The wireless communicationdevice of claim 30, wherein the predetermined timing offset depends on anumerology used, and there is more than one timing offset for onenumerology.
 38. The wireless communication device of claim 30, whereinthe predetermined timing offset is indicated in the RAR message.
 39. Amethod of operating a wireless communication device, the methodcomprising: transmitting a preamble on a Physical Random Access Channel(PRACH); receiving a Random Access Response (RAR) message containing anuplink (UL) grant; transmitting, on a Physical Uplink Shared Channel(PUSCH), a first message wherein the first message is a Msg3 message andhas a first time resource allocation; and transmitting, on the PUSCH, asecond message wherein the second message is a non-Msg3 message and hasa second time resource allocation, the first and second time resourceallocations being different by a predetermined timing offset.
 40. Themethod of claim 39, wherein the predetermined timing offset is a numberof slots and is based on a numerology used.